| Home |
| AS10K1 Manual |
| EMU10K1 Project page |
| Audigy2 Install Guide |
EMU10K1
Prerequisites:
(1) kernel-headers
(check /usr/include/linux for *.h files, if so, then it's probably installed.
for rpm-based distros:
rpm -qa|grep headers
--should return something like:
glibc-kernheaders -or- kernel-headers
(2) kernel-source
(check /usr/src for a 'linux' or the like, directory)
If this is missing install kernel-source for your matching kernel.
(3) a '.config' file in /usr/src/'your_linux_source_here'
If Red Hat or any other distro that offers predone configs usually in
/usr/src/linux-2.4/configs, I.e.: cp /usr/src/linux-2.4/configs/your_archtype_config
/usr/src/linux-2.4.
Also you can generate a '.config' file running 'make menuconfig' in
/usr/src/linux_version by running 'make menuconfig' in that directory.
Grabbing the driver from CVS of http://sf.net/projects/emu10k1
(1) Goto the CVS page of http://sf.net/projects/emu10k1
(2) Open a teminal an 'su -' to root and 'cd ~'
(3) Issue command: cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/emu10k1 login
(4) Issue command: cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/emu10k1 co emu10k1
This will give you an 'emu10k1' directory in /root that contains the source code to get
Audigy2 running in Linux.
Compiling and installing the emu10k1 sound driver module:
(1) change directory to emu10k1 'cd emu10k1'
(2) run the commands to compile and install the driver and tools, NOTE: DO NOT download and try to
use separate package of emu-tools as they are NOT compatable with this driver.
commands: 'make ; make ; make install ; make tools ; make install-tools'
This will give you a working emu10k1 driver in /lib/modules/your_kernel_version/
kernel/sound/emu10k1.
If this step fails, please check prerequisites and make sure everything is set up
correctly, check compile errors to see what is borked.
(3) edit /etc/modules.conf or the proper file for sound if you have to run 'update-modules' and
place the following lines in /etc/modules.conf , or, the latter:
alias sound emu10k1
alias sound-slot-0 emu10k1
alias sound-service-0-0 sound
post-install emu10k1 /usr/local/etc/audigy-script restore
pre-remove emu10k1 /usr/local/etc/audigy-script save
I've had alot of questions about the last two lines and what they do. The last two execute
and save your emu10k1.conf settings and runs audigy-script when the modules is loaded and
saves mixer settings upon exit so that when you reboot or reload your sound driver
your mixer settings will be saved as they were before, pretty cool huh?
Tweaking your card:
Take note: you DO have a working emu-tools that was compiled and installed when you
issued 'make tools ; make install-tools'. These tools are compatable with your driver,
to some extent, as they really haven't been updated to support the Audigy2 soundcard,
but with the proper settings, should work. Check in the same directory of this document
for emu10k1.conf for 4.1 and emu10k1.conf for 6.1. /usr/local/etc/emu10k1.conf is the
settings file and is executed when /usr/local/etc/audigy-script is run. There is no
need to run audigy-script on it's own if you have the above lines referencing it
in modules.conf.
Considerations before modprobe:
You may have certain processes locking your drivers so that you cannot unload them. Also
make sure you remove any other soundcard references from /etc/modules.conf, unless
you plan on using more than one soundcard. Processes like ESD sound server and
ARTS sound server are common to be running if either using KDE or GNOME. If possible,
I would suggest turning these off completely. If you cannot load the emu10k1 module, try:
ps aux|grep -i esd ; ps aux|grep -i arts
If loaded...
killall -9 esd -or- killall -9 arts
Also make sure you have no sound applets loaded as well as they can lock the driver
module so that it can't be removed.
If previous drivers are still loaded, remove them with the 'rmmod' command, to check which
possible drivers may still be loaded, do with 'lsmod'
Lastly, 'modprobe emu10k1', hopefully all goes well!
*note: If 'rmmod old_sound_module_name' doesn't work and everything is set up correctly
(modules.conf is correct as well as /usr/local/etc/emu10k1) a quick fix is a simple reboot.
*note2: We ran into a problem with a user running 'bttv' tv card module. If this module is
loaded BEFORE emu10k1, it can lead to problems. A quick fix is to put in a startup script:
/sbin/rmmod bttv
/sbin/modprobe emu10k1
/sbin/modprobe bttv